Fix build path issues due to conflict with Tycho and OSGI builds #384
+19
−6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description of changes:
Removes an explicit
bin.includes
entry fortarget/classes
and instead uses the Tycho packaging plugin to include build classes at the root of the JAR. The classpath entry inMETA-INF/MANIFEST.MF
now includes the root dir as a classpath root.This will make Eclipse happy while developing in the IDE while meanwhile ensuring that built classes are included correctly in the Tycho produced JAR. It likely does break the ability to export a plugin JAR from the Eclipse IDE directly, but I do not believe this to be of major concern since they can and should be produced via Maven build.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.